Clarified not to delete or disable a previous TDE protector key after a rotation. #10119
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prmerger-automator
bot
requested review from
Pietervanhove,
WilliamDAssafMSFT,
VanMSFT and
MashaMSFT
|
@sanjayd : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
azure-sql/svc
Change sent to author
security/subsvc
labels
|
Learn Build status updates of commit 2c1f17e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@Pietervanhove - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A user I was supporting in the past disabled their previous TDE Protector key in keyvault after rotating it. This caused their database to become unavailable following the rotation. Earlier in the doc it is advised that old backups and log files may still require access to the old key and to keep it active until sys.dm_db_log_info shows it's no longer in use, but this !important text box only mentions not to delete it. Adding a clarification to keep it active would help avoid similar situations.